Cassie

Wahay!

Wonderful! Thanks for your patience.

Hi there! We've pressed some knobs and switched things off and on again and you should be all set now. We generated a new token for you. If you go to the install page, and hard refresh you should see the new token and the correct 'business' tier instructions I think this little blip happened because your business membership was from quite a while ago - 2014! Something must have gone a bit wonky during those years. Thanks for all the support and sorry for the trouble.

We have some demos here! https://stackblitz.com/@gsap-dev/collections/gsap-nuxtjs-starters

This may be down to the fact that nuxt is doing the build on the server - are you checking whether you're running registerPlugin client side? Something like this depending on your setup if (process.client) { gsap.registerPlugin(SplitText) } or if (typeof window !== 'undefined') { gsap.registerPlugin(SplitText) }

Hi again, Just a note to say we're looking into it as a matter of urgency. 'member' should have been 'business' on the install page. Apologies for leading you down a bad path here. We'll pop back as soon as we know more

Hey Jordan, little sidenote - that token won't just automatically pull from the .env file - you have to set your environment up to manage them, I think this is the right way in nuxt. https://github.com/nuxt-community/dotenv-module Otherwise - I'm not seeing any GSAP specific errors in that netlify log. Your issue isn't a 403 with the private repo, the issue is here - Cannot find module @rollup/rollup-.... npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try npm i again after removing both package-lock.json and node_modules directory Here's a thread. Sorry I can't help more here! https://github.com/nuxt/nuxt/issues/25006

Hey there, What does your package.json look like currently?

Pleasure, it was on my to-do list, good to get a little nudge. Thanks!

Heya, thanks for that log. Are you using yarn locally or npm? This line is giving me a little red flag, I wonder if you're using npm locally and then yarn on Netlify? warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. There's a known issue with yarn and private registries - it's discussed in this thread. So maybe these steps from @Prasanna might help? If you are using npm locally and yarn on Netlify I'd suggest setting up Netlify to use npm commands instead.

That should download now!

Pushing up a fix now! Typo. Just popped the page together quickly this morning, sorry!

Is it working locally for you? Just an issue when deploying?

Hey folks. Sorry about this. Sounds frustrating. I tried to debug for you, but I stepped through the process and my site built deployed first time. Are you using npm? Can you give me any more info?